Call Enhancement In Virtual Desktop Infrastructure

ABSTRACT

Calls run through a virtual desktop infrastructure server are enhanced by testing communication network conditions and selecting, based on the test results, a media channel from a set of supported media channels, including a media channel that is routed through the virtual desktop infrastructure server and encapsulated in a protocol for exchanging data for virtual desktop applications and a more direct media channel that uses a network socket pair between a media server and a personal computing device and bypasses the virtual desktop infrastructure server. In some implementations, call data of multiple types and/or from multiple sources are merged into a single virtual channel of the protocol for exchanging data for virtual desktop applications.

BACKGROUND

Enterprise entities rely upon several modes of communication to supporttheir operations, including telephone, email, internal messaging, andthe like. These separate modes of communication have historically beenimplemented by service providers whose services are not integrated withone another. The disconnect between these services, in at least somecases, requires information to be manually passed by users from oneservice to the next. Furthermore, some services, such as telephonyservices, are traditionally delivered via on-premises solutions, meaningthat remote workers and those who are generally increasingly mobile maybe unable to rely upon them. One solution is by way of a unifiedcommunications as a service (UCaaS) platform, which includes severalcommunications services integrated over a network, such as the Internet,to deliver a complete communication experience regardless of physicallocation.

SUMMARY

Disclosed herein are, inter alia, implementations of systems andtechniques for call enhancements in virtual desktop infrastructure.

One aspect of this disclosure is a method including testingcommunications network conditions for a network socket pair connectionbetween a personal computing device and a media server that bypasses avirtual desktop infrastructure server to obtain direct connection testresults; based on the direct connection test results, selecting a mediachannel from among a set of media channels for a call initiated usingthe virtual desktop infrastructure server, wherein the set of mediachannels includes a first media channel using the network socket pairconnection between the personal computing device and the media serverand a second media channel that is routed through the virtual desktopinfrastructure server and encapsulated in a protocol for exchanging datafor virtual desktop applications; and transferring media data betweenthe media server and the personal computing device using the selectedmedia channel to enable the call.

One aspect of this disclosure is a personal computing device, includinga network interface, a processor, and a memory, wherein the memorystores instructions executable by the processor to: test communicationsnetwork conditions for a network socket pair connection between apersonal computing device and a media server that bypasses a virtualdesktop infrastructure server to obtain direct connection test results;based on the direct connection test results, select a media channel fromamong a set of media channels for a call initiated using the virtualdesktop infrastructure server, wherein the set of media channelsincludes a first media channel using the network socket pair connectionbetween the personal computing device and the media server and a secondmedia channel that is routed through the virtual desktop infrastructureserver and encapsulated in a protocol for exchanging data for virtualdesktop applications; and transfer media data between the media serverand the personal computing device using the selected media channel toenable the call.

One aspect of this disclosure is a non-transitory computer-readablestorage medium, comprising executable instructions that, when executedby a processor, facilitate performance of operations, including testingcommunications network conditions for a network socket pair connectionbetween a personal computing device and a media server that bypasses avirtual desktop infrastructure server to obtain direct connection testresults; based on the direct connection test results, selecting a mediachannel from among a set of media channels for a call initiated usingthe virtual desktop infrastructure server, wherein the set of mediachannels includes a first media channel using the network socket pairconnection between the personal computing device and the media serverand a second media channel that is routed through the virtual desktopinfrastructure server and encapsulated in a protocol for exchanging datafor virtual desktop applications; and transferring media data betweenthe media server and the personal computing device using the selectedmedia channel to enable the call.

BRIEF DESCRIPTION OF THE DRAWINGS

This disclosure is best understood from the following detaileddescription when read in conjunction with the accompanying drawings. Itis emphasized that, according to common practice, the various featuresof the drawings are not to-scale. On the contrary, the dimensions of thevarious features are arbitrarily expanded or reduced for clarity.

FIG. 1 is a block diagram of an example of an electronic computing andcommunications system.

FIG. 2 is a block diagram of an example internal configuration of acomputing device of an electronic computing and communications system.

FIG. 3 is a block diagram of an example of a software platformimplemented by an electronic computing and communications system.

FIG. 4 is a block diagram of an example of a virtual desktopinfrastructure system configured to enable calls using a virtual desktopinstance.

FIG. 5 is a block diagram of an example of a system configured to enablecalls using a virtual desktop instance that illustrates the flow ofmedia data to support a call.

FIG. 6 is a flowchart of an example of a technique for selecting a mediachannel to support a call initiated using a virtual desktopinfrastructure server.

FIG. 7 is a flowchart of an example of a technique for testingcommunications network conditions for network socket pair connections insystem configured to enable calls using a virtual desktop instance.

FIG. 8 is a flowchart of an example of a technique for testingcommunications network conditions for network socket pair connections insystem configured to enable calls using a virtual desktop instance.

FIG. 9 is a flowchart of an example of a technique for selecting a mediachannel to support a call initiated using a virtual desktopinfrastructure server.

DETAILED DESCRIPTION

A service often offered to large groups of users remotely is virtualdesktop infrastructure (VDI), which allows user access a desktopinterface that is provided by a server. This desktop interface providesaccess to applications that run on the operating system used by thevirtual desktop instance, which may be a different operating system thanthat used by a personal computing device that a user uses to remotelyaccess the virtual desktop.

Client software for a UCaaS platform can be run on a virtual desktopinstance. For example, UCaaS client software running on a VDI server canbe used to facilitate the participation of a user in calls (e.g., videoconferencing calls or voice-only calls) from their personal computingdevice that is connected to the VDI server. The VDI server may relaysome or all data used to facilitate the call between one or more serversof a UCaaS platform and the user's personal computing device. It isadvantageous in some circumstances to route media data (e.g., audioand/or video data) for a call more directly between a media server ofthe UCaaS platform and the personal computing device to bypass the VDIserver. This practice is often referred to as media offloading. Inappropriate circumstances, media offloading can conserve computingresources on the VDI server, conserve network bandwidth that would otherwise be used to relay the media data for the call, which can be arelatively high data rate, and reduce latency in the call, which can asignificant factor in perceived call quality. This comes at the expenseof an increase in the use of processing resources on the personalcomputing device, which has to run media coders and decoders for themedia streams locally. However, in some circumstances, media offloadingcan degrade call quality.

Implementations of this disclosure address problems such as these byenabling a personal computing device that is entering a call setup byclient software running in a VDI server to test the communicationnetwork conditions and select a media channel for transferring mediadata of the call from a set of supported media channels to suit thecurrent conditions. For example, the set of supported media channels mayinclude (1) a relatively direct connection to the media server that VDIserver bypasses and uses a network socket pair connection (e.g., using aUser Datagram Protocol (UDP) socket pair) between the media server andthe personal computing device; (2) a second media channel that is routedthrough the VDI server and encapsulated in a protocol (e.g., theIndependent Computing Architecture (ICA) protocol or the Remote DesktopProtocol (RDP) protocol) for exchanging data for virtual desktopapplications; and/or (3) a third media channel using a network socketpair connection (e.g., using a UDP socket pair) between the personalcomputing device and the VDI server. In some implementations, the moredirect connection using the first media channel is preferred and may beused whenever test results for this direct connection satisfy acriterion (e.g., sufficient data throughput and/or low enough latency.In some implementations, the third media channel is preferred to thesecond media channel, and the second media channel is selected when thefirst media channel is disqualified, and the third media channelsatisfies a criterion. If both the first media channel and the thirdmedia channel are disqualified than the second media channel may beselected. In some implementations, test results for multiple supportedmedia channels may be compared to each other and a media channel may beselected based on the comparison.

When the second media channel that that is routed through the VDI serverand encapsulated in a protocol (e.g., the ICA protocol or the RDPprotocol) for exchanging data for virtual desktop applications is used,it can be advantageous to conserve the number of virtual channels of theprotocol that are used by a given call. For example, multiple mediastreams (e.g., from different call participants, may be merged into asingle virtual channel of the protocol. In some implementations, all ofthe data exchanged during the call (e.g., including control data, audiodata, video data, and share data) may be merged into a single virtualchannel of the protocol. Conserving virtual channel usage may enable aVDI system to support a high volume of calls, making the system morescalable. Merging different types of call data into a single virtualchannel of the protocol may also enable custom prioritization thevarious traffic types by a phone agent or a meeting agent.

To describe some implementations in greater detail, reference is firstmade to examples of hardware and software structures used to implementcall enhancements in virtual desktop infrastructure. FIG. 1 is a blockdiagram of an example of an electronic computing and communicationssystem 100, which can be or include a distributed computing system(e.g., a client-server computing system), a cloud computing system, aclustered computing system, or the like.

The system 100 includes one or more customers, such as customers 102Athrough 102B, which may each be a public entity, private entity, oranother corporate entity or individual that purchases or otherwise usessoftware services, such as of a UCaaS platform provider. Each customercan include one or more clients. For example, as shown and withoutlimitation, the customer 102A can include clients 104A through 104B, andthe customer 102B can include clients 104C through 104D. A customer caninclude a customer network or domain. For example, and withoutlimitation, the clients 104A through 104B can be associated orcommunicate with a customer network or domain for the customer 102A andthe clients 104C through 104D can be associated or communicate with acustomer network or domain for the customer 102B.

A client, such as one of the clients 104A through 104D, may be orotherwise refer to one or both of a client device or a clientapplication. Where a client is or refers to a client device, the clientcan comprise a computing system, which can include one or more computingdevices, such as a mobile phone, a tablet computer, a laptop computer, anotebook computer, a desktop computer, or another suitable computingdevice or combination of computing devices. Where a client instead is orrefers to a client application, the client can be an instance ofsoftware running on a customer device (e.g., a client device or anotherdevice). In some implementations, a client can be implemented as asingle physical unit or as a combination of physical units. In someimplementations, a single physical unit can include multiple clients.

The system 100 can include a number of customers and/or clients or canhave a configuration of customers or clients different from thatgenerally illustrated in FIG. 1. For example, and without limitation,the system 100 can include hundreds or thousands of customers, and atleast some of the customers can include or be associated with a numberof clients.

The system 100 includes a datacenter 106, which may include one or moreservers. The datacenter 106 can represent a geographic location, whichcan include a facility, where the one or more servers are located. Thesystem 100 can include a number of datacenters and servers or caninclude a configuration of datacenters and servers different from thatgenerally illustrated in FIG. 1. For example, and without limitation,the system 100 can include tens of datacenters, and at least some of thedatacenters can include hundreds or another suitable number of servers.In some implementations, the datacenter 106 can be associated orcommunicate with one or more datacenter networks or domains, which caninclude domains other than the customer domains for the customers 102Athrough 102B.

The datacenter 106 includes servers used for implementing softwareservices of a UCaaS platform. The datacenter 106 as generallyillustrated includes an application server 108, a database server 110,and telephony server 112. The servers 108 through 112 can each be acomputing system, which can include one or more computing devices, suchas a desktop computer, a server computer, or another computer capable ofoperating as a server, or a combination thereof. A suitable number ofeach of the servers 108 through 112 can be implemented at the datacenter106. The UCaaS platform uses a multi-tenant architecture in whichinstallations or instantiations of the servers 108 through 112 is sharedamongst the customers 102A through 102B.

In some implementations, one or more of the servers 108 through 112 canbe a non-hardware server implemented on a physical device, such as ahardware server. In some implementations, a combination of two or moreof the application server 108, the database server 110, and thetelephony server 112 can be implemented as a single hardware server oras a single non-hardware server implemented on a single hardware server.In some implementations, the datacenter 106 can include servers otherthan or in addition to the servers 108 through 112, for example, a mediaserver, a proxy server, or a web server.

The application server 108 runs web-based software services deliverableto a client, such as one of the clients 104A through 104D. As describedabove, the software services may be of a UCaaS platform. For example,the application server 108 can implement all or a portion of a UCaaSplatform, for example, including conferencing software, messagingsoftware, and/or other intra-party or inter-party communicationssoftware. The application server 108 may, for example, be or include aunitary Java Virtual Machine (JVM).

In some implementations, the application server 108 can include anapplication node, which can be a process executed on the applicationserver 108. For example, and without limitation, the application nodecan be executed in order to deliver software services to a client, suchas one of the clients 104A through 104D, as part of a softwareapplication. The application node can be implemented using processingthreads, virtual machine instantiations, or other computing features ofthe application server 108. In some such implementations, theapplication server 108 can include a suitable number of applicationnodes, depending upon a system load or other characteristics associatedwith the application server 108. For example, and without limitation,the application server 108 can include two or more nodes forming a nodecluster. In some such implementations, the application nodes implementedon a single application server 108 can run on different hardwareservers.

The database server 110 stores, manages, or otherwise provides data fordelivering software services of the application server 108 to a client,such as one of the clients 104A through 104D. In particular, thedatabase server 110 may implement one or more databases, tables, orother information sources suitable for use with a software applicationimplemented using the application server 108. The database server 110may include a data storage unit accessible by software executed on theapplication server 108. A database implemented by the database server110 may be a relational database management system (RDBMS), an objectdatabase, an XML database, a configuration management database (CMDB), amanagement information base (MIB), one or more flat files, othersuitable non-transient storage mechanisms, or a combination thereof. Thesystem 100 can include one or more database servers, in which eachdatabase server can include one, two, three, or another suitable numberof databases configured as or comprising a suitable database type orcombination thereof.

In some implementations, one or more databases, tables, other suitableinformation sources, or portions or combinations thereof may be stored,managed, or otherwise provided by one or more of the elements of thesystem 100 other than the database server 110, for example, the client104 or the application server 108.

The telephony server 112 enables network-based telephony and webcommunications from and to clients of a customer, such as the clients104A through 104B for the customer 102A or the clients 104C through 104Dfor the customer 102B. Some or all of the clients 104A through 104D maybe voice over internet protocol (VOIP)-enabled devices configured tosend and receive calls over a network, for example, a network 114. Inparticular, the telephony server 112 includes a session initiationprotocol (SIP) zone and a web zone. The SIP zone enables a client of acustomer, such as the customer 102A or 102B, to send and receive callsover the network 114 using SIP requests and responses. The web zoneintegrates telephony data with the application server 108 to enabletelephony-based traffic access to software services run by theapplication server 108. Given the combined functionality of the SIP zoneand the web zone, the telephony server 112 may be or include acloud-based private branch exchange (PBX) system.

The SIP zone receives telephony traffic from a client of a customer anddirects same to a destination device. The SIP zone may include one ormore call switches for routing the telephony traffic. For example, toroute a VOIP call from a first VOIP-enabled client of a customer to asecond VOIP-enabled client of the same customer, the telephony server112 may initiate a SIP transaction between a first client and the secondclient using a PBX for the customer. However, in another example, toroute a VOIP call from a VOIP-enabled client of a customer to a clientor non-client device (e.g., a desktop phones which is not configured forVOIP communication) which is not VOIP-enabled, the telephony server 112may initiate a SIP transaction via a VOIP gateway that transmits the SIPsignal to a public switched telephone network (PSTN) system for outboundcommunication to the non-VOIP-enabled client or non-client phone. Hence,the telephony server 112 may include a PSTN system and may in some casesaccess an external PSTN system.

The telephony server 112 includes one or more session border controllers(SBCs) for interfacing the SIP zone with one or more aspects external tothe telephony server 112. In particular, an SBC can act as anintermediary to transmit and receive SIP requests and responses betweenclients or non-client devices of a given customer with clients ornon-client devices external to that customer. When incoming telephonytraffic for delivery to a client of a customer, such as one of theclients 104A through 104D, originating from outside the telephony server112 is received, a SBC receives the traffic and forwards it to a callswitch for routing to the client.

In some implementations, the telephony server 112, via the SIP zone, mayenable one or more forms of peering to a carrier or customer premise.For example, Internet peering to a customer premise may be enabled toease the migration of the customer from a legacy provider to a serviceprovider operating the telephony server 112. In another example, privatepeering to a customer premise may be enabled to leverage a privateconnection terminating at one end at the telephony server 112 and at theother at a computing aspect of the customer environment. In yet anotherexample, carrier peering may be enabled to leverage a connection of apeered carrier to the telephony server 112.

In some such implementations, a SBC or telephony gateway within thecustomer environment may operate as an intermediary between the SBC ofthe telephony server 112 and a PSTN for a peered carrier. When anexternal SBC is first registered with the telephony server 112, a callfrom a client can be routed through the SBC to a load balancer of theSIP zone, which directs the traffic to a call switch of the telephonyserver 112. Thereafter, the SBC may be configured to communicatedirectly with the call switch.

The web zone receives telephony traffic from a client of a customer, viathe SIP zone, and directs same to the application server 108 via one ormore Domain Name System (DNS) resolutions. For example, a first DNSwithin the web zone may process a request received via the SIP zone andthen deliver the processed request to a web service which connects to asecond DNS at or otherwise associated with the application server 108.Once the second DNS resolves the request, it is delivered to thedestination service at the application server 108. The web zone may alsoinclude a database for authenticating access to a software applicationfor telephony traffic processed within the SIP zone, for example, asoftphone.

The clients 104A through 104D communicate with the servers 108 through112 of the datacenter 106 via the network 114. The network 114 can be orinclude, for example, the Internet, a local area network (LAN), a widearea network (WAN), a virtual private network (VPN), or another publicor private means of electronic computer communication capable oftransferring data between a client and one or more servers. In someimplementations, a client can connect to the network 114 via a communalconnection point, link, or path, or using a distinct connection point,link, or path. For example, a connection point, link, or path can bewired, wireless, use other communications technologies, or a combinationthereof.

The network 114, the datacenter 106, or another element, or combinationof elements, of the system 100 can include network hardware such asrouters, switches, other network devices, or combinations thereof. Forexample, the datacenter 106 can include a load balancer 116 for routingtraffic from the network 114 to various servers associated with thedatacenter 106. The load balancer 116 can route, or direct, computingcommunications traffic, such as signals or messages, to respectiveelements of the datacenter 106.

For example, the load balancer 116 can operate as a proxy, or reverseproxy, for a service, such as a service provided to one or more remoteclients, such as one or more of the clients 104A through 104D, by theapplication server 108, the telephony server 112, and/or another server.Routing functions of the load balancer 116 can be configured directly orvia a DNS. The load balancer 116 can coordinate requests from remoteclients and can simplify client access by masking the internalconfiguration of the datacenter 106 from the remote clients.

In some implementations, the load balancer 116 can operate as afirewall, allowing or preventing communications based on configurationsettings. Although the load balancer 116 is depicted in FIG. 1 as beingwithin the datacenter 106, in some implementations, the load balancer116 can instead be located outside of the datacenter 106, for example,when providing global routing for multiple datacenters. In someimplementations, load balancers can be included both within and outsideof the datacenter 106.

FIG. 2 is a block diagram of an example internal configuration of acomputing device 200 of an electronic computing and communicationssystem, for example, a computing device which implements one or more ofthe client 104, the application server 108, the database server 110, orthe telephony server 112 of the system 100 shown in FIG. 1.

The computing device 200 includes components or units, such as aprocessor 202, a memory 204, a bus 206, a power source 208, peripherals210, a user interface 212, a network interface 214, other suitablecomponents, or a combination thereof. One or more of the memory 204, thepower source 208, the peripherals 210, the user interface 212, or thenetwork interface 214 can communicate with the processor 202 via the bus206.

The processor 202 is a central processing unit, such as amicroprocessor, and can include single or multiple processors havingsingle or multiple processing cores. Alternatively, the processor 202can include another type of device, or multiple devices, now existing orhereafter developed, configured for manipulating or processinginformation. For example, the processor 202 can include multipleprocessors interconnected in one or more manners, including hardwired ornetworked, including wirelessly networked. For example, the operationsof the processor 202 can be distributed across multiple devices or unitsthat can be coupled directly or across a local area or other suitabletype of network. The processor 202 can include a cache, or cache memory,for local storage of operating data or instructions.

The memory 204 includes one or more memory components, which may each bevolatile memory or non-volatile memory. For example, the volatile memoryof the memory 204 can be random access memory (RAM) (e.g., a DRAMmodule, such as DDR SDRAM) or another form of volatile memory. Inanother example, the non-volatile memory of the memory 204 can be a diskdrive, a solid state drive, flash memory, phase-change memory, oranother form of non-volatile memory configured for persistent electronicinformation storage. The memory 204 may also include other types ofdevices, now existing or hereafter developed, configured for storingdata or instructions for processing by the processor 202. In someimplementations, the memory 204 can be distributed across multipledevices. For example, the memory 204 can include network-based memory ormemory in multiple clients or servers performing the operations of thosemultiple devices.

The memory 204 can include data for immediate access by the processor202. For example, the memory 204 can include executable instructions216, application data 218, and an operating system 220. The executableinstructions 216 can include one or more application programs, which canbe loaded or copied, in whole or in part, from non-volatile memory tovolatile memory to be executed by the processor 202. For example, theexecutable instructions 216 can include instructions for performing someor all of the techniques of this disclosure. The application data 218can include user data, database data (e.g., database catalogs ordictionaries), or the like. In some implementations, the applicationdata 218 can include functional programs, such as a web browser, a webserver, a database server, another program, or a combination thereof.The operating system 220 can be, for example, Microsoft Windows®, Mac OSX®, or Linux®; an operating system for a mobile device, such as asmartphone or tablet device; or an operating system for a non-mobiledevice, such as a mainframe computer.

The power source 208 includes a source for providing power to thecomputing device 200. For example, the power source 208 can be aninterface to an external power distribution system. In another example,the power source 208 can be a battery, such as where the computingdevice 200 is a mobile device or is otherwise configured to operateindependently of an external power distribution system. In someimplementations, the computing device 200 may include or otherwise usemultiple power sources. In some such implementations, the power source208 can be a backup battery.

The peripherals 210 includes one or more sensors, detectors, or otherdevices configured for monitoring the computing device 200 or theenvironment around the computing device 200. For example, theperipherals 210 can include a geolocation component, such as a globalpositioning system location unit. In another example, the peripheralscan include a temperature sensor for measuring temperatures ofcomponents of the computing device 200, such as the processor 202. Insome implementations, the computing device 200 can omit the peripherals210.

The user interface 212 includes one or more input interfaces and/oroutput interfaces. An input interface may, for example, be a positionalinput device, such as a mouse, touchpad, touchscreen, or the like; akeyboard; or another suitable human or machine interface device. Anoutput interface may, for example, be a display, such as a liquidcrystal display, a cathode-ray tube, a light emitting diode display, orother suitable display.

The network interface 214 provides a connection or link to a network(e.g., the network 114 shown in FIG. 1). The network interface 214 canbe a wired network interface or a wireless network interface. Thecomputing device 200 can communicate with other devices via the networkinterface 214 using one or more network protocols, such as usingEthernet, transmission control protocol (TCP), internet protocol (IP),power line communication, an IEEE 802.X protocol (e.g., Wi-Fi,Bluetooth, ZigBee, etc.), infrared, visible light, general packet radioservice (GPRS), global system for mobile communications (GSM),code-division multiple access (CDMA), Z-Wave, another protocol, or acombination thereof.

FIG. 3 is a block diagram of an example of a software platform 300implemented by an electronic computing and communications system, forexample, the system 100 shown in FIG. 1. The software platform 300 is aUCaaS platform accessible by clients of a customer of a UCaaS platformprovider, for example, the clients 104A through 104B of the customer102A or the clients 104C through 104D of the customer 102B shown inFIG. 1. For example, the software platform 300 may be a multi-tenantplatform instantiated using one or more servers at one or moredatacenters including, for example, the application server 108, thedatabase server 110, and the telephony server 112 of the datacenter 106shown in FIG. 1.

The software platform 300 includes software services accessible usingone or more clients. For example, a customer 302, which may, forexample, be the customer 102A, the customer 102B, or another customer,as shown includes four clients—a desk phone 304, a computer 306, amobile device 308, and a shared device 310. The desk phone 304 is adesktop unit configured to at least send and receive calls and includesan input device for receiving a telephone number or extension to dial toand an output device for outputting audio and/or video for a call inprogress. The computer 306 is a desktop, laptop, or tablet computerincluding an input device for receiving some form of user input and anoutput device for outputting information in an audio and/or visualformat. The mobile device 308 is a smartphone, wearable device, or othermobile computing aspect including an input device for receiving someform of user input and an output device for outputting information in anaudio and/or visual format. The desk phone 304, the computer 306, andthe mobile device 308 may generally be considered personal devicesconfigured for use by a single user. The shared device 312 is a deskphone, a computer, a mobile device, or a different device which mayinstead be configured for use by multiple specified or unspecified users

Each of the clients 304 through 310 includes or runs on a computingdevice configured to access at least a portion of the software platform300. In some implementations, the customer 302 may include additionalclients not shown. For example, the customer 302 may include multipleclients of one or more client types (e.g., multiple desk phones,multiple computers, etc.) and/or one or more clients of a client typenot shown in FIG. 3 (e.g., wearable devices, televisions other than asshared devices, or the like). For example, the customer 302 may havetens or hundreds of desk phones, computers, mobile devices, and/orshared devices.

The software services of the software platform 300 generally relate tocommunications tools, but are in no way limited in scope. As shown, thesoftware services of the software platform 300 include telephonysoftware 312, virtualized meeting software 314, messaging software 316,and other software 318. Some or all of the software 312 through 318 usescustomer configurations 320 specific to the customer 302. The customerconfigurations 320 may, for example, be data stored within a database orother data store at a database server, such as the database server 110shown in FIG. 1.

The telephony software 312 enables telephony traffic between ones of theclients 304 through 310 and other telephony-enabled devices, which maybe other ones of the clients 304 through 310, other VOIP-enabled clientsof the customer 302, non-VOIP-enabled devices of the customer 302,VOIP-enabled clients of another customer, non-VOIP-enabled devices ofanother customer, or other VOIP-enabled clients or non-VOIP-enableddevices. For example, the telephony software 312 may be implementedusing one or more both of an application server and a telephony server,such as the application server 108 and the telephony server 112 shown inFIG. 1. Calls sent or received using the telephony software 312 may, forexample, be sent or received using the desk phone 304, a softphonerunning on the computer 306, a mobile application running on the mobiledevice 308, or using the shared device 310 where same includes telephonyfeatures.

The virtualized meeting software 314 enables audio, video, and/or otherforms of virtualized meetings between multiple devices, such as tofacilitate a conference between the users of those devices. Thevirtualized meeting software 314 can include functionality for hosting,presenting scheduling, joining, or otherwise participating in avirtualized meeting. The virtualized meeting software 314 may furtherinclude functionality for recording some or all of a virtualized meetingand/or documenting a transcript for the virtualized meeting.

The messaging software 316 enables instant messaging, unified messaging,and other types of messaging communications between multiple devices,such as to facilitate a chat or like virtual conversation between usersof those devices. The unified messaging functionality of the messagingsoftware 316 may, for example, refer to email messaging which includesvoicemail transcription service delivered in email format.

The other software 318 enables other functionality of the softwareplatform 300. Examples of the other software 318 include, but are notlimited to, device management software, resource provisioning anddeployment software, administrative software, third party integrationsoftware, and the like. In one particular example, the other software318 can include code for selecting a media channel from a set of optionsfor a call made using virtual desktop infrastructure in order to enhancethe call.

Features of the software services of the software platform 300 may beintegrated with one another to provide a unified experience for users.For example, the messaging software 316 may include a user interfaceelement configured to initiate a call with another user of the customer302. In another example, the telephony software 312 may includefunctionality for elevating a telephone call to a virtualized meeting.In yet another example, the virtualized meeting software 314 may includefunctionality for sending and receiving instant messages betweenparticipants and/or other users of the customer 302. In yet anotherexample, the virtualized meeting software 314 may include functionalityfor file sharing between participants and/or other users of the customer302. In some implementations, some or all of the software 312 through318 may be combined into a single software application run on clients ofthe customer, such as one or more of the clients 304-310.

FIG. 4 is a block diagram of an example of a virtual desktopinfrastructure system 400 configured to enable calls using a virtualdesktop instance. The virtual desktop infrastructure system 400 includesa virtual desktop infrastructure host 410; a virtual desktopinfrastructure client 420 (e.g., a VDI thin client); and a virtualdesktop infrastructure client 422. A virtual desktop image 412, whichincludes an application virtual desktop infrastructure client 414, isprovided by the virtual desktop infrastructure host 410. The virtualdesktop infrastructure client 420 includes an application virtualdesktop infrastructure plugin 430, which includes a phone agent 440 anda meeting agent 450. The virtual desktop infrastructure client 422includes an application virtual desktop infrastructure plugin 432, whichincludes a phone agent 442 and a meeting agent 452. Note that inpractice the virtual desktop infrastructure host 410 may support manymore virtual desktop infrastructure clients than the two depicted inFIG. 4. For example, the virtual desktop infrastructure system 400 maybe used to implement the technique 600 of FIG. 6. For example, thetechnique 600 of FIG. 6 may implanted by the virtual desktopinfrastructure client 420 or the virtual desktop infrastructure client422.

Calls may be supported in the virtual desktop infrastructure system 400by the cooperation of the application virtual desktop infrastructureclient 414 with a virtual desktop infrastructure plugin (430 or 432).For example, a call may include streaming of audio from two or moreparticipants, including a user of the virtual desktop infrastructureclient 420 being used to place or answer the call using the phone agent440. For example, a call may include streaming of audio and video fromtwo or more participants, including a user of the virtual desktopinfrastructure client 420 being used to host or attend the call usingthe meeting agent 450, which may facilitate video calls/conferencing.

The application virtual desktop infrastructure client 414 is installedin the virtual desktop image 412 that is instantiated on the virtualdesktop infrastructure host 410. The virtual desktop infrastructureplugin 430 is installed in virtual desktop infrastructure client 420.For example, the virtual desktop infrastructure client 420 run on apersonal computing device (e.g., a laptop, smartphone, or a tablet). Thevirtual desktop infrastructure client 420 may run on a differentoperating system (e.g., Windows, OS X, Linux, or Android) than thevirtual desktop image 412 and it may run on a different operating systemthan other virtual desktop infrastructure clients. For example, here thevirtual desktop infrastructure client 420 may run on Windows and thevirtual desktop infrastructure client 422 runs on Linux. As a result,the virtual desktop infrastructure plugin 430, the phone agent 440, andthe meeting agent 450 are Windows versions of these software; while thevirtual desktop infrastructure plugin 432, the phone agent 442, and themeeting agent 452 are a Linux version of these software. In someimplementations, phone agents 440 and 442 are just different instancesof the same software components. In some implementations, meeting agents450 and 452 are just different instances of the same softwarecomponents. The virtual desktop infrastructure system 400 may enable awide variety of devices to access the call functionality provided by theapplication virtual desktop infrastructure client 414.

FIG. 5 is a block diagram of an example of a system 500 configured toenable calls using a virtual desktop instance that illustrates the flowof media data to support a call. The system 500 includes a media server510; a virtual desktop infrastructure server 520; and a personalcomputing device 530. For example, the system 500 may be used toimplement the technique 600 of FIG. 6. For example, the technique 600 ofFIG. 6 may implemented by the personal computing device 530.

For example, the media server 510 may be the telephone server 112. Insome implementations, the media server 510 is a public branch exchangeserver. In some implementations, the media server 510 is a multimediarouter (MMR) server.

For example, the virtual desktop infrastructure server 520 may run thevirtual desktop infrastructure host 410, including one or more virtualdesktop images that have the application virtual desktop infrastructureclient 414 installed. For example, the virtual desktop infrastructureserver 520 may include a computing device, such as the computing device200 of FIG. 2.

For example, the personal computing device 530 may be a laptop, asmartphone, a tablet. For example, the personal computing device 530 maybe one of the clients 304 through 310. For example, the personalcomputing device 530 may run a virtual desktop infrastructure client(e.g., the virtual desktop infrastructure client 420) the includes anapplication virtual desktop infrastructure plugin with a phone agentand/or a meeting agent for participating in calls. In someimplementations, a virtual desktop infrastructure client (e.g., a VDIthin client) running on the personal computing device 530 acts as aslave and a virtual desktop infrastructure host running on the virtualdesktop infrastructure server 520 acts as a master in a master/slaveinteraction to facilitate a call. For example, the personal computingdevice 530 may include a computing device, such as the computing device200 of FIG. 2.

For example, a call may be initiated by the virtual desktopinfrastructure server 520 in response to request from the personalcomputing device 530 (e.g., caused by input from a user such as dialing)or in response to an inbound call message from the media server 510 oran associated server that supports calls using the media server 510. Aspart of the setup for the call, commands or other control data may beexchanged between the media server 510 and the virtual desktopinfrastructure server 520 via a control channel 540 through acommunications network. For example, the control channel 540 may utilizea cryptographic protocol such as Transport Layer Security (TLS) 1.2 orSecure Sockets Layer (SSL). The virtual desktop infrastructure server520 may be configured to relay some or all of the control data received,including call parameters, to the personal computing device 530 via acontrol channel 542. For example, the control channel 542 may beencapsulated in a protocol (e.g., the ICA protocol or the RDP protocol)for exchanging data for virtual desktop applications. In particular, thevirtual desktop infrastructure server 520 may pass an identifier for themedia server 510 to personal computing device 530 to facilitate theestablishment of a more direct connection between the media server 510and personal computing device 530 that bypasses the virtual desktopinfrastructure server 520 to enable media offloading.

The personal computing device 530 may be configured to implement thetechnique 600 of FIG. 6 to test the communications network conditionsand select a media channel for bearing media data for the call from aset of supported media channels. The set of supported media channels mayinclude a first media channel 550 using a network socket pair connectionbetween the personal computing device 530 and the media server 510. Theset of supported media channels may include a second media channel 552that is routed through the virtual desktop infrastructure server 520 andencapsulated in a protocol (e.g., ICA or RDP) for exchanging data forvirtual desktop applications. The set of supported media channels mayinclude a third media channel 554 using a second network socket pairconnection between the personal computing device 530 and the virtualdesktop infrastructure server 520. If an indirect connection that routesmedia data through the virtual desktop infrastructure server 520 isused, then a media channel 556 between the virtual desktopinfrastructure server 520 and the media server 510 will also beestablished. For example, the media channels 550, 554, and/or 556 mayutilize a network socket pair for their respective endpoints accordingto a transport protocol, such as, for example, UDP or Secure Real-timeTransport Protocol (SRTP). In some implementations, a media channel(e.g., 550 or 554) may use a customized port range (e.g., UDP ports9,000-10,000). Once a media channel has been selected for the call, theselected media channel (e.g., the media channel 550, the media channel552, or the media channel 554) may be used to transfer between the mediaserver 510 and the personal computing device 530 to enable the call.Selecting a media channel for the call dynamically based on tests ofcommunications network conditions may enhance calls in virtual desktopinfrastructure system by improve resource utilization while maintainingcall quality.

To further describe implementations in greater detail, reference is nextmade to examples of techniques which may be performed to provide callenhancements in virtual desktop infrastructure. FIG. 6 is a flowchart ofan example of a technique 600 for selecting a media channel to support acall initiated using a virtual desktop infrastructure server. FIG. 7 isa flowchart of an example of a technique 700 for testing communicationsnetwork conditions for network socket pair connections in systemconfigured to enable calls using a virtual desktop instance. FIG. 8 is aflowchart of an example of a technique 800 for testing communicationsnetwork conditions for network socket pair connections in systemconfigured to enable calls using a virtual desktop instance. FIG. 9 is aflowchart of an example of a technique 900 for selecting a media channelto support a call initiated using a virtual desktop infrastructureserver.

The techniques 600, 700, 800, and/or 900 can be executed using computingdevices, such as the systems, hardware, and software described withrespect to FIGS. 1-5. The techniques 600, 700, 800, and/or 900 can beperformed, for example, by executing a machine-readable program or othercomputer-executable instructions, such as routines, instructions,programs, or other code. The steps, or operations, of the techniques600, 700, 800, and/or 900 or another technique, method, process, oralgorithm described in connection with the implementations disclosedherein can be implemented directly in hardware, firmware, softwareexecuted by hardware, circuitry, or a combination thereof.

For simplicity of explanation, each of the techniques 600, 700, 800, and900 are depicted and described herein as a series of steps oroperations. However, the steps or operations in accordance with thisdisclosure can occur in various orders and/or concurrently.Additionally, other steps or operations not presented and describedherein may be used. Furthermore, not all illustrated steps or operationsmay be required to implement a technique in accordance with thedisclosed subject matter.

Referring to FIG. 6, the technique 600 for selecting a media channel tosupport a call initiated using a virtual desktop infrastructure serveris shown. At 602, the technique 600 includes transmitting, using apersonal computing device (e.g., the personal computing device 530), arequest for a call to a virtual desktop infrastructure server (e.g., thevirtual desktop infrastructure server 520). For example, the request maybe sent using application software (e.g., the phone agent 440 or themeeting agent 450) running over application virtual desktopinfrastructure plugin (e.g., the application VDI plugin 430) that runson the personal computing device. The request may be received by anapplication virtual desktop infrastructure client (e.g., the applicationVDI client 414) running in a virtual desktop instance running on thevirtual desktop infrastructure server. For example, the request may beencapsulated in a protocol (e.g., the ICA protocol or the RDP protocol)for exchanging data for virtual desktop applications. The virtualdesktop infrastructure server may in turn, responsive to the request,initiate a call via control communications with a media server (e.g.,the media server 510). For example, the media server may be a publicbranch exchange server. For example, the media server may be a publicbranch exchange server. For example, the media server may be amultimedia router server. For example, the request may be transmittedusing a network interface (e.g., the network interface 214) of thepersonal computing device.

At 604, the technique 600 includes receiving, using the personalcomputing device, call parameters from the virtual desktopinfrastructure server, wherein the call parameters include an identifierfor the media server. For example, the identifier for the media servermay include an Internet Protocol (IP) address for the media server. Forexample, the identifier for the media server may include an IP addressfor the media server. For example, the identifier for the media servermay include an internet domain name used by the media server. The callparameters may include other data that may be used to facilitate thesetup and maintenance of the call, such a port number to be usedtransferring data of the call. For example, the call parameters may berelayed an application virtual desktop infrastructure client (e.g., theapplication VDI client 414) running in a virtual desktop instancerunning on the virtual desktop infrastructure server. For example, thecall parameters may be encapsulated in a protocol (e.g., the ICAprotocol or the RDP protocol) for exchanging data for virtual desktopapplications. For example, the call parameters may be received using anetwork interface (e.g., the network interface 214) of the personalcomputing device.

At 606, the technique 600 includes testing communications networkconditions for one or more network socket pair connections. Thetechnique 600 may include testing communications network conditions fora network socket pair connection between the personal computing deviceand the media server that bypasses the virtual desktop infrastructureserver to obtain direct connection test results. For example, thenetwork socket pair may include sockets of a transport layer protocol(e.g., UDP, Transmission Control Protocol (TCP), Stream ControlTransmission Protocol (SCTP), or Datagram Congestion Control Protocol(DCCP)). For example, the network socket pair may include a socket atthe media server and a socket at the personal computing device that maybe used to send media data between the two devices using the applicablecommunications network protocol. In some implementations, a socket pairis selected from designated ranges of UDP ports for the two devicesbeing connected. For example, testing communications network conditionsfor the network socket pair connection between the personal computingdevice and the media server that bypasses the virtual desktopinfrastructure server may include performing a handshake test using thenetwork socket pair connection. For example, a handshake test mayinclude an exchange of RTP Control Protocol (RTCP) packets back andforth between the personal computing device and the media server. Insome implementations, the direct connection test results include anetwork latency metric. In some implementations, the direct connectiontest results include a network data throughput metric. At 606, thetechnique 600 may also include testing communications network conditionsfor a second network socket pair connection between the personalcomputing device and the virtual desktop infrastructure server to obtainindirect connection test results. For example, testing communicationsnetwork conditions for the second network socket pair connection betweenthe personal computing device and the virtual desktop infrastructureserver may include performing a handshake test using the second networksocket pair connection. In some implementations, the indirect connectiontest results include a network latency metric. In some implementations,the indirect connection test results include a network data throughputmetric. For example, at 606, testing communications network conditionsfor one or more network socket pair connections may include implementingthe technique 700 of FIG. 7. For example, at 606, testing communicationsnetwork conditions for one or more network socket pair connections mayinclude implementing the technique 800 of FIG. 8.

At 608, the technique 600 includes, based on the direct connection testresults, selecting a media channel from among a set of media channelsfor a call initiated using the virtual desktop infrastructure server.The set of media channels includes a first media channel (e.g., thefirst media channel 550) using the network socket pair connectionbetween the personal computing device and the media server and a secondmedia channel (e.g., the second media channel 552) that is routedthrough the virtual desktop infrastructure server and encapsulated in aprotocol (e.g., the ICA protocol or the RDP protocol) for exchangingdata for virtual desktop applications. In some implementations, the setof media channels also includes a media channel (e.g., the third mediachannel 554) using the second network socket pair connection between thepersonal computing device and the virtual desktop infrastructure server.Selecting the media channel may also be based on the indirect connectiontest results. For example, if the direct connection test results satisfya criterion (e.g., a connection is established with acceptablethroughput and/or latency), then the first media channel may be selectedfor use in the call. For example, if the direct connection test resultsfail to satisfy a criterion and the indirect connection test resultssatisfy a criterion (e.g., a connection is established with acceptablethroughput and/or latency), then the third media channel may be selectedfor use in the call. For example, if both the direct connection testresults and the indirect connection test results fail to satisfy acriterion, then the second media channel may be selected for use in thecall. In some implementations, the direct connection test results arecompared to the indirect connection test results and media channel withthe better connection test results is selected for use in the call. Insome implementations, the set of media channels includes more mediachannels (e.g., direct and/or indirect media channels using differentprotocols for transport across a communications network) for whichconnection test results are determined and a media channel is selectedbased on these additional connection test results.

At 610, the technique 600 includes transferring media data between themedia server and the personal computing device using the selected mediachannel to enable the call. For example, the media data transferredusing the selected media channel includes packets of audio data. In someimplementations, the media data transferred using the selected mediachannel includes packets of video data. When the selected media channelis the second media channel that is routed through the virtual desktopinfrastructure server and encapsulated in the protocol (e.g., ICA orRDP) for exchanging data for virtual desktop applications, the technique600 may include merging multiple streams of media data in a singlevirtual channel of the protocol. For example, audio streams for multipleparticipants in the call may be merged in a single ICA virtual channel.In some implementations, data for the call, including the media data andcall control data, is transferred in a single virtual channel of theprotocol (e.g., ICA or RDP). For example, a single virtual channel maybe used to transfer all data for the call. Merging call data ofdifferent types (e.g., media data, control data, share data) and/or fromdifferent sources (e.g., different call participants) may provide one ormore benefits, such as conserving the number virtual channels used forthe call and enabling custom prioritization of call data within the callto enhance call quality. Using a media channel selected based on dynamiccommunications network conditions may enable a system for supportingcalls with virtual desktop infrastructure to more efficiently scalewhile preserving or enhancing call quality.

Referring to FIG. 7, the technique 700 for testing communicationsnetwork conditions for network socket pair connections in systemconfigured to enable calls using a virtual desktop instance is shown. At702, the technique 700 includes testing communications networkconditions for a network socket pair connection between a personalcomputing device (e.g., the personal computing device 530) and a mediaserver (e.g., the media server 510) that bypasses a virtual desktopinfrastructure server (e.g., the virtual desktop infrastructure server520) to obtain direct connection test results. For example, testingcommunications network conditions for the network socket pair connectionbetween the personal computing device and the media server that bypassesthe virtual desktop infrastructure server may include performing ahandshake test using the network socket pair connection. For example, ahandshake test may include an exchange of RTCP packets back and forthbetween the personal computing device and the media server. In someimplementations, the direct connection test results include a networklatency metric. In some implementations, the direct connection testresults include a network data throughput metric.

At 704, if the direct connection test results satisfy a criterion, thenthe technique 700 includes, at 706, continuing to selection of the mediachannel. For example, using the first media channel 550 may bepreferred, so it may be sufficient to check the direct connection testresults and select, at 608, the first media channel based on the directconnection test results.

At 704, if the direct connection test results do not satisfy acriterion, then the technique 700 includes, at 708, testingcommunications network conditions for a second network socket pairconnection between the personal computing device and the virtual desktopinfrastructure server to obtain indirect connection test results. Forexample, testing communications network conditions for the secondnetwork socket pair connection between the personal computing device andthe virtual desktop infrastructure server may include performing ahandshake test using the second network socket pair connection. In someimplementations, the indirect connection test results include a networklatency metric. In some implementations, the indirect connection testresults include a network data throughput metric.

At 710, the technique 700 includes continuing to selection of the mediachannel. For example, where the direct connection test results fail tosatisfy the criterion, the indirect connection test results are alsodetermined and checked to prepare for selecting, at 608, a media channelbased on the direct connection test results and also based on theindirect connection test results. For example, the indirect connectiontest results may be considered to select between the second mediachannel 552 and the third media channel 544 after the first mediachannel 550 has been ruled out based on the direct connection testresults.

Referring to FIG. 8, the technique 800 for testing communicationsnetwork conditions for network socket pair connections in systemconfigured to enable calls using a virtual desktop instance is shown. At802, the technique 800 includes testing communications networkconditions for a network socket pair connection between a personalcomputing device (e.g., the personal computing device 530) and a mediaserver (e.g., the media server 510) that bypasses a virtual desktopinfrastructure server (e.g., the virtual desktop infrastructure server520) to obtain direct connection test results. For example, testingcommunications network conditions for the network socket pair connectionbetween the personal computing device and the media server that bypassesthe virtual desktop infrastructure server may include performing ahandshake test using the network socket pair connection. For example, ahandshake test may include an exchange of RTCP packets back and forthbetween the personal computing device and the media server. In someimplementations, the direct connection test results include a networklatency metric. In some implementations, the direct connection testresults include a network data throughput metric.

At 804, the technique 800 includes testing communications networkconditions for a second network socket pair connection between thepersonal computing device and the virtual desktop infrastructure serverto obtain indirect connection test results. For example, testingcommunications network conditions for the second network socket pairconnection between the personal computing device and the virtual desktopinfrastructure server may include performing a handshake test using thesecond network socket pair connection. In some implementations, theindirect connection test results include a network latency metric. Insome implementations, the indirect connection test results include anetwork data throughput metric.

At 806, the technique 800 includes comparing the direct connection testresults to the indirection connection test results. For example,throughputs and/or latencies measured for the respective network socketpair connections may be compared. In some implementations, thecomparison may be handicapped to favor a preferred media channel (e.g.,the direct connection tests results may be enhanced for comparison wherethe first media channel 550 is preferred for system utilizationpurposes.

At 808, the technique 800 includes continuing to selection, at 608, ofthe media channel. For example, at 608, the media channel may beselected based on the comparison of the direct connection test resultsto the indirection connection test results.

Referring to FIG. 9, the technique 900 for selecting a media channel tosupport a call initiated using a virtual desktop infrastructure serveris shown. The technique 600 incorporates the use of timers as part of ascheme to test communications network conditions and select a media modefor a call. At 902, the technique 900 includes performing a VDI plugindetection operation. At 904, if a VDI plugin was not successfullydetected, then the technique 900 includes, at 906, selecting the use ofa fallback mode for media streaming for the call. For example, afallback mode may include running media codecs for the call on the VDIserver, which in turn transfers media data to and/or from a personalcomputing device that is the user interface to the call at a fulluncompressed data rate via a standard channel of a VDI protocol beingused. At 904, if a VDI plugin was successfully detected, then thetechnique 900 includes, at 908, starting a media mode detectionoperation. For example, step 908 may be a starting point for testing todetect the media mode to be used for a call. At 910, a 15 second timeris started. If a complete test result is not achieved within 15 seconds,then the technique 900 includes, at 906, selecting the use of thefallback mode for media streaming for the call. While the 15 secondtimer is still running, the technique 900 includes, at 912 trying todetect the status of a media channel that uses a UDP socket pairconnection between the VDI server and the personal computing device. Forexample, the techniques described in relation to step 708 in FIG. 7 maybe used to test media channel that uses a UDP socket pair connectionbetween the VDI server and the personal computing device. When the UDPsocket pair connection between the VDI server and the personal computingdevice is tested, a 1 second timer is started and, at 914, a detectionresult for the media channel that uses a UDP socket pair connectionbetween the VDI server and the personal computing device is set orstored for later use. One second later, at 916, the technique includestrying to detect the status of a direct mode media channel, which uses amore direct connection between the personal computing device and a mediaserver supporting the call. The direct mode media channel may bypass theVDI server. For example, the direct mode media channel may use a UDPsocket pair connection between the media server and the personalcomputing device. For example, the techniques described in relation tostep 702 in FIG. 7 may be used to test the direct mode media channel.

At 918, if the direct mode detection test succeeded, then the technique900 includes, at 920 selecting the use of the direct mode for mediastreaming for the call. For example, the direct mode may use a UDPsocket pair connection between the media server and the personalcomputing device to transfer media data for the call. At 918, thetechnique 900 includes setting a 1 second timer and waiting up to 1second to get a result. Otherwise, if the timer expires, the detectionresult is failure, the technique 900 proceeds to check the next option.

At 922, if the UDP mode detection test succeeded, then the technique 900includes, at 924 selecting the use of the UDP mode for media streamingfor the call. For example, the UDP mode may use a UDP socket pairconnection between the VDI server and the personal computing device totransfer media data for the call.

At 922, if the UDP mode detection test failed, then the technique 900includes, at 926 selecting the use of an ICA mode for media streamingfor the call. For example, the ICA mode may use a virtual channel of theICA protocol between the VDI server and the personal computing device totransfer media data for the call. The media data transferred using ICAmode, like UDP mode, and Direct mode, may be compressed to conservenetwork bandwidth resources. A plugin running on the personal computingdevice may use one or more media codecs to process media data locally,instead of relying on an application running on VDI server to performthese functions.

The implementations of this disclosure can be described in terms offunctional block components and various processing operations. Suchfunctional block components can be realized by a number of hardware orsoftware components that perform the specified functions. For example,the disclosed implementations can employ various integrated circuitcomponents (e.g., memory elements, processing elements, logic elements,look-up tables, and the like), which can carry out a variety offunctions under the control of one or more microprocessors or othercontrol devices. Similarly, where the elements of the disclosedimplementations are implemented using software programming or softwareelements, the systems and techniques can be implemented with aprogramming or scripting language, such as C, C++, Java, JavaScript,assembler, or the like, with the various algorithms being implementedwith a combination of data structures, objects, processes, routines, orother programming elements.

Functional aspects can be implemented in algorithms that execute on oneor more processors. Furthermore, the implementations of the systems andtechniques disclosed herein could employ a number of conventionaltechniques for electronics configuration, signal processing or control,data processing, and the like. The words “mechanism” and “component” areused broadly and are not limited to mechanical or physicalimplementations, but can include software routines in conjunction withprocessors, etc. Likewise, the terms “system” or “tool” as used hereinand in the figures, but in any event based on their context, may beunderstood as corresponding to a functional unit implemented usingsoftware, hardware (e.g., an integrated circuit, such as an ASIC), or acombination of software and hardware. In certain contexts, such systemsor mechanisms may be understood to be a processor-implemented softwaresystem or processor-implemented software mechanism that is part of orcallable by an executable program, which may itself be wholly or partlycomposed of such linked systems or mechanisms.

Implementations or portions of implementations of the above disclosurecan take the form of a computer program product accessible from, forexample, a computer-usable or computer-readable medium. Acomputer-usable or computer-readable medium can be a device that can,for example, tangibly contain, store, communicate, or transport aprogram or data structure for use by or in connection with a processor.The medium can be, for example, an electronic, magnetic, optical,electromagnetic, or semiconductor device.

Other suitable mediums are also available. Such computer-usable orcomputer-readable media can be referred to as non-transitory memory ormedia, and can include volatile memory or non-volatile memory that canchange over time. A memory of an apparatus described herein, unlessotherwise specified, does not have to be physically contained by theapparatus, but is one that can be accessed remotely by the apparatus,and does not have to be contiguous with other memory that might bephysically contained by the apparatus.

While the disclosure has been described in connection with certainimplementations, it is to be understood that the disclosure is not to belimited to the disclosed implementations but, on the contrary, isintended to cover various modifications and equivalent arrangementsincluded within the scope of the appended claims, which scope is to beaccorded the broadest interpretation so as to encompass all suchmodifications and equivalent structures as is permitted under the law.

What is claimed is:
 1. A method, comprising: testing communicationsnetwork conditions for a network socket pair connection between apersonal computing device and a media server that bypasses a virtualdesktop infrastructure server to obtain direct connection test results;based on the direct connection test results, selecting a media channelfrom among a set of media channels for a call initiated using thevirtual desktop infrastructure server, wherein the set of media channelsincludes a first media channel using the network socket pair connectionbetween the personal computing device and the media server and a secondmedia channel that is routed through the virtual desktop infrastructureserver and encapsulated in a protocol for exchanging data for virtualdesktop applications; and transferring media data between the mediaserver and the personal computing device using the selected mediachannel to enable the call.
 2. The method of claim 1, wherein thenetwork socket pair connection between the personal computing device andthe media server is a first network socket pair connection, and furthercomprising: testing communications network conditions for a secondnetwork socket pair connection between the personal computing device andthe virtual desktop infrastructure server to obtain indirect connectiontest results; wherein the set of media channels includes a media channelusing the second network socket pair connection between the personalcomputing device and the virtual desktop infrastructure server; andwherein selecting the media channel is also based on the indirectconnection test results.
 3. The method of claim 1, wherein testingcommunications network conditions for the network socket pair connectionbetween the personal computing device and the media server that bypassesthe virtual desktop infrastructure server comprises: performing ahandshake test using the network socket pair connection.
 4. The methodof claim 1, wherein the direct connection test results include a networklatency metric.
 5. The method of claim 1, wherein the direct connectiontest results include a network data throughput metric.
 6. The method ofclaim 1, wherein the selected media channel is the media channel that isrouted through the virtual desktop infrastructure server andencapsulated in the protocol for exchanging data for virtual desktopapplications, and further comprising: merging multiple streams of mediadata in a single virtual channel of the protocol.
 7. The method of claim1, wherein the selected media channel is the media channel that isrouted through the virtual desktop infrastructure server andencapsulated in the protocol for exchanging data for virtual desktopapplications, and further comprising: transferring data for the call,including the media data and call control data, in a single virtualchannel of the protocol.
 8. The method of claim 7, wherein the singlevirtual channel is used to transfer all data for the call.
 9. The methodof claim 1, wherein the media server is a public branch exchange server.10. The method of claim 1, wherein the media data transferred using theselected media channel includes packets of audio data.
 11. The method ofclaim 1, wherein the media data transferred using the selected mediachannel includes packets of video data.
 12. The method of claim 1,further comprising: transmitting, using the personal computing device, arequest for the call to the virtual desktop infrastructure server; andreceiving, using the personal computing device, call parameters from thevirtual desktop infrastructure server, wherein the call parametersinclude an identifier for the media server.
 13. A personal computingdevice, comprising: a network interface, a processor, and a memory,wherein the memory stores instructions executable by the processor to:test communications network conditions for a network socket pairconnection between a personal computing device and a media server thatbypasses a virtual desktop infrastructure server to obtain directconnection test results; based on the direct connection test results,select a media channel from among a set of media channels for a callinitiated using the virtual desktop infrastructure server, wherein theset of media channels includes a first media channel using the networksocket pair connection between the personal computing device and themedia server and a second media channel that is routed through thevirtual desktop infrastructure server and encapsulated in a protocol forexchanging data for virtual desktop applications; and transfer mediadata between the media server and the personal computing device usingthe selected media channel to enable the call.
 14. The personalcomputing device of claim 13, wherein the network socket pair connectionbetween the personal computing device and the media server is a firstnetwork socket pair connection, and the memory stores instructionsexecutable by the processor to: test communications network conditionsfor a second network socket pair connection between the personalcomputing device and the virtual desktop infrastructure server to obtainindirect connection test results; wherein the set of media channelsincludes a media channel using the second network socket pair connectionbetween the personal computing device and the virtual desktopinfrastructure server; and wherein selecting the media channel is alsobased on the indirect connection test results.
 15. The personalcomputing device of claim 13, wherein the memory stores instructionsexecutable by the processor to: perform a handshake test using thenetwork socket pair connection.
 16. The personal computing device ofclaim 13, wherein the selected media channel is the media channel thatis routed through the virtual desktop infrastructure server andencapsulated in the protocol for exchanging data for virtual desktopapplications, and the memory stores instructions executable by theprocessor to: merge multiple streams of media data in a single virtualchannel of the protocol.
 17. The personal computing device of claim 13,wherein the selected media channel is the media channel that is routedthrough the virtual desktop infrastructure server and encapsulated inthe protocol for exchanging data for virtual desktop applications, andthe memory stores instructions executable by the processor to: transferdata for the call, including the media data and call control data, in asingle virtual channel of the protocol.
 18. The personal computingdevice of claim 13, wherein the media server is a public branch exchangeserver.
 19. A non-transitory computer-readable storage medium,comprising executable instructions that, when executed by a processor,facilitate performance of operations, comprising: testing communicationsnetwork conditions for a network socket pair connection between apersonal computing device and a media server that bypasses a virtualdesktop infrastructure server to obtain direct connection test results;based on the direct connection test results, selecting a media channelfrom among a set of media channels for a call initiated using thevirtual desktop infrastructure server, wherein the set of media channelsincludes a first media channel using the network socket pair connectionbetween the personal computing device and the media server and a secondmedia channel that is routed through the virtual desktop infrastructureserver and encapsulated in a protocol for exchanging data for virtualdesktop applications; and transferring media data between the mediaserver and the personal computing device using the selected mediachannel to enable the call.
 20. The non-transitory computer-readablestorage medium of claim 19, wherein the network socket pair connectionbetween the personal computing device and the media server is a firstnetwork socket pair connection, and further comprising executableinstructions that, when executed by a processor, facilitate performanceof operations, comprising: testing communications network conditions fora second network socket pair connection between the personal computingdevice and the virtual desktop infrastructure server to obtain indirectconnection test results; wherein the set of media channels includes amedia channel using the second network socket pair connection betweenthe personal computing device and the virtual desktop infrastructureserver; and wherein selecting the media channel is also based on theindirect connection test results.